[SPARK-8658] [SQL] [FOLLOW-UP] AttributeReference's equals method compares all the members#9761
[SPARK-8658] [SQL] [FOLLOW-UP] AttributeReference's equals method compares all the members#9761gatorsmile wants to merge 2 commits intoapache:masterfrom
Conversation
|
Test build #46069 has finished for PR 9761 at commit
|
|
@nongli I saw you have a related discussion with @chenghao-intel . The failed test case was introduced in your PR #9480. I am not sure the root reason why we intentionally exclude Based on my understanding, in a case-insensitive HiveContext, we still should detect their differences when the case of |
|
This change looks good to me. The failing test is not valid anymore and should be changed to verify that the hash codes are not equal. |
|
Ok. I will also add three more lines for covering the new |
|
Test build #46095 has finished for PR 9761 at commit
|
|
Thanks! Merging to master and 1.6. |
…res all the members Based on the comment of cloud-fan in #9216, update the AttributeReference's hashCode function by including the hashCode of the other attributes including name, nullable and qualifiers. Here, I am not 100% sure if we should include name in the hashCode calculation, since the original hashCode calculation does not include it. marmbrus cloud-fan Please review if the changes are good. Author: gatorsmile <gatorsmile@gmail.com> Closes #9761 from gatorsmile/hashCodeNamedExpression. (cherry picked from commit 0158ff7) Signed-off-by: Michael Armbrust <michael@databricks.com>
Based on the comment of @cloud-fan in #9216, update the AttributeReference's hashCode function by including the hashCode of the other attributes including name, nullable and qualifiers.
Here, I am not 100% sure if we should include name in the hashCode calculation, since the original hashCode calculation does not include it.
@marmbrus @cloud-fan Please review if the changes are good.